\documentclass{article}

\title{Meeting Notes}

\author{Jeffrey Robinson}

\date{January 20, 2011}

\begin{document}

\maketitle

\pagestyle{empty}

\thispagestyle{empty}

\begin{center} {\bf Overview} \end{center}

\noindent The purpose of the meeting was to get an idea of where to start and how to 
procede.  We first determined that we all need to do some basic research into 
operating systems to see how they function in practice.  We located a list of 
operating systems websites to begin learning about how they function and 
tutorials on how things are implemented.  We also determed that the best 
way to proceed would be to use the waterfall methodology because of the 
size and complexity of our project.   From this we determined a set of short 
term goals so that we can start working on the long term goals and then 
the SRS for our project.  \\
\mbox{}

\noindent Short Term Goals:

\begin{itemize}

\item{Determine Main Components of an operating system}
\item{Determing how those components function}
\item{Determing how components function among each other}
\item{Determing the boot sequence of the bootloaders and the kernel}
\\
\mbox{}

\begin{center} {\bf Specifics} \end{center}

We spent a lot of time talking about what an operating system does and how 
it boots up.   We also talked about different parts of the system and what is
absolutely required to just have something executing.  We have determined 
that there are only at most four required subsystems in an operating system:
CPU Management, Memory Management, Device Management, and Disk Management.\\
\mbox{}

Even though we have these four subsystems we might be needing more because 
we could not think of others or maybe we could condense these into three 
because disks are a type of device.  The other problem we are trying to 
determing is the order of initalization of each system and what 
pre-intialization must be done to make the system capable of running each 
subsytem.  We have looked at a [4] to dermine how linux initializes everything 
which was really helpful.

We also worked on determining if we could find other capable computer science 
students who can join the project.  We believe that we should try for two 
reasons: CS students would benefit greatly from this type of work due to 
the research involved and also the knowledge gained, the students learn 
how to work in a group in a real project instead of class projects where 
doing just enough will not cut it.  

We have determined a couple of students and previous students who 
we believe to be capable of joining us and they  are : Brian Eddy, Eric Davis, 
Larry Phillmon, and Frank Cheng.  

To finish the meeting we determined that we will meet again on Jan 20
on skype to continue our work.  Also on Friday Jan 21 we will have a 
physical meeting on campus to work on topics.  We also determined that 
skype will be the best way to proceed because it allows both voice and 
text chatting.  If neccessary we will find some other form of collaboration
methods.

Finally the google code site is : https://code.google.com/p/jeffdavegabeos/
\\
\mbox{}

\begin{center} {\bf References} \end{center}


[1]\underline{Operating System Development Site} \\
http://www.nondot.org/sabre/os/articles


[2]\underline{Bios Boot specification} \\
http://www.nondot.org/sabre/os/files/Booting/BIOSBootSpecsV1.01.pdf

[3]\underline{Operating System Development Site} \\
http://wiki.osdev.org/Main\_Page

[4]\underline{Kernel Loading and Order of Initalization} \\
http://duartes.org/gustavo/blog/post/kernel-boot-process

[5]\underline{Has information on main bootloader} \\
http://duartes.org/gustavo/blog/post/how-computers-boot-up

[6]\underline{Tutorials and Information on different parts of the OS} \\
http://www.osdever.net/tutorials/index

\end{itemize}

\end{document}